port: normalize protocol-relative remote host as https (upstream c49d424e3)#183
Merged
Conversation
Ported-from: t3code c49d424
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ports upstream t3code commit c49d424 ("Normalize protocol-relative remote host input as https", upstream pingdotgg#3971) into gits. Tracked as plan.md §1b.
normalizeRemoteBaseUrlnow strips leading slashes before scheme detection, so//host,///host, and//https://hostinputs normalize tohttps://instead of producing empty/invalid hosts. Upstream's tests come along; upstream-only drift (RemoteBackendUrlInvalidError, protocol allowlist) was NOT ported — fork keeps its plainnew URL.Verified: forced
turbo run typecheck(14/14), shared-package vitestremote.test.ts(10/10 incl. 5 new),oxfmt --checkclean.🤖 Generated with Claude Code